Power management for integrated access and backhaul networks

ABSTRACT

In one of its example aspects the technology disclosed herein concerns an Integrated Access and Backhaul (IAB) node ( 24 ) that communicates over a radio interface. The IAB node comprises mobile-termination circuitry ( 50 ), distributed unit circuitry ( 52 ), and processor circuitry ( 54 ). The mobile-termination circuitry is configured to transmit over the radio interface with a parent node. The distributed unit circuitry is configured to transmit over the radio interface with a child node. The processor circuitry is configured to manage transmission power utilized by the IAB node by taking into consideration both transmission by the mobile-termination circuitry and transmission by the distributed unit circuitry. Other example aspects of the technology disclosed herein concern transmission power reporting by such IAB node, transmission power prioritization by such IAB node; transmission power governance for the distributed unit circuitry for such IAB node; and method of operating such IAB node(s).

TECHNICAL FIELD

The technology relates to wireless communications, and particularly topower management for Integrated Access and Backhaul (IAB) networks.

BACKGROUND ART

A radio access network typically resides between wireless devices, suchas user equipment (UEs), mobile phones, mobile stations, or any otherdevice having wireless termination, and a core network. Example of radioaccess network types includes the GRAN, GSM radio access network; theGERAN, which includes EDGE packet radio services; UTRAN, the UMTS radioaccess network; E-UTRAN, which includes Long-Term Evolution; andg-UTRAN, the New Radio (NR).

A radio access network may comprise one or more access nodes, such asbase station nodes, which facilitate wireless communication or otherwiseprovides an interface between a wireless terminal and atelecommunications system. A non-limiting example of a base station caninclude, depending on radio access technology type, a Node B (“NB”), anenhanced Node B (“eNodeB” or “eNB”), a home eNB (“HeNB”), a “gNodeB” or“gNB” for a New Radio [“NR” ] technology system, or some other similarterminology.

The 3rd Generation Partnership Project (“3GPP”) is a group that, e.g.,develops collaboration agreements such as 3GPP standards that aim todefine globally applicable technical specifications and technicalreports for wireless communication systems. Various 3GPP documents maydescribe certain aspects of radio access networks. Overall architecturefor a fifth generation system, e.g., the 5G System, also called “NR” or“New Radio”, as well as “NG” or “Next Generation”, is shown in FIG. 1,and is also described in 3GPP TS 38.300. The 5G NR network is comprisedof NG RAN (Next Generation Radio Access Network) and 5GC (5G CoreNetwork). As shown, NGRAN is comprised of gNBs (e.g., 5G Base stations)and ng-eNBs (i.e. LTE base stations). An Xn interface exists betweengNB-gNB, between (gNB)-(ng-eNB) and between (ng-eNB)-(ng-eNB). The Xn isthe network interface between NG-RAN nodes. Xn-U stands for Xn UserPlane interface and Xn-C stands for Xn Control Plane interface. A NGinterface exists between 5GC and the base stations (i.e. gNB & ng-eNB).A gNB node provides NR user plane and control plane protocolterminations towards the UE, and is connected via the NG interface tothe 5GC. The 5G NR (New Radio) gNB is connected to AMF (Access andMobility Management Function) and UPF (User Plane Function) in 5GC (5GCore Network).

In some cellular mobile communication systems and networks, such asLong-Term Evolution (LTE) and New Radio (NR), a service area is coveredby one or more base stations, where each of such base stations may beconnected to a core network by fixed-line backhaul links (e.g., opticalfiber cables). In some instances, due to weak signals from the basestation at the edge of the service area, users tend to experienceperformance issues, such as: reduced data rates, high probability oflink failures, etc. A relay node concept has been introduced to expandthe coverage area and increase the signal quality. As implemented, therelay node may be connected to the base station using a wirelessbackhaul link.

In 3rd Generation Partnership Project (3GPP), the relay node concept forthe fifth generation (5G) cellular system has been discussed andstandardized, where the relay nodes may utilize the same 5G radio accesstechnologies (e.g., New Radio (NR)) for the operation of services toUser Equipment (UE) (access link) and connections to the core network(backhaul link) simultaneously. These radio links may be multiplexed intime, frequency, and/or space. This system may be referred to asIntegrated Access and Backhaul (IAB).

Some such cellular mobile communication systems and networks maycomprise IAB-donors and IAB-nodes, where an IAB-donor may provideinterface to a core network to UEs and wireless backhaulingfunctionality to IAB-nodes; and additionally, an IAB-node may provideIAB functionality combined with wireless self-backhauling capabilities.

A Donor IAB Node is a node that provides access of corenetwork/backhaul/radio resource control functionality to the IABnetwork. A Donor IAB node may comprise a CU, e.g., a “Central Unit,” ormore properly, a gNB-CU, and a distributed unit, e.g., DU. The centralunit CU is a logical node hosting RRC, SDAP and PDCP protocols of thegNB or RRC and PDCP protocols of the en-gNB that controls the operationof one or more gNB-DUs. The gNB-CU terminates the F1 interface connectedwith the gNB-DU” according to 3GPP TS38.401.

A non-Donor IAB node may either be a relay IAB node or a client device,e.g., a wireless terminal or UE. A relay IAB mode may comprise a mobiletermination unit, MT, and a distributed unit, DU. An IAB node that is awireless terminal or mobile device may comprise transceiver circuitry,e.g., a transmitter and received, and processor circuitry.

Power management for a wireless terminal such as a UE has obviousimportance since wireless terminals are typically battery powered. Powermanagement can also be an issue for base stations including IAB nodes,even though base stations tend to be connected to a power grid most ofthe time rather than being battery operated. But base stations may bebattery operated at least some of the time, for example should there bea massive power outage. Base stations benefit from power management foryet other reasons, such as spectral regulations concerning (frequency)sidelobe emissions. Moreover, there is the potential that 5G networksoverall may consume significantly greater energy than LTE networks,particularly a 5G network with many small cells and if beamformingequipment is utilized.

What is needed are methods, apparatus, and/or techniques which involveor facilitate power management for Integrated Access and Backhaul (IAB)nodes.

SUMMARY OF INVENTION

In one example, an Integrated Access and Backhaul (IAB) node thatcommunicates over a radio interface, the IAB node comprising:mobile-termination circuitry configured to transmit over the radiointerface with a parent node; distributed unit circuitry configured totransmit over the radio interface with a child node; processor circuitryconfigured to manage transmission power utilized by the IAB node bytaking into consideration both transmission by the mobile-terminationcircuitry and transmission by the distributed unit circuitry.

In one example, a method in an Integrated Access and Backhaul (IAB) nodethat communicates over a radio interface, the method node comprising:using mobile-termination circuitry to transmit over the radio interfacewith a parent node; using distributed unit circuitry to transmit overthe radio interface with a child node; managing transmission powerutilized by the IAB node by taking into consideration both transmissionby the mobile-termination circuitry and transmission by the distributedunit circuitry.

In one example, a donor Integrated Access and Backhaul (IAB) node in anIntegrated Access and Backhaul (IAB) network, the donor IAB nodecomprising: processor circuitry configured to designate one or more IABnodes of the Integrated Access and Backhaul (IAB) network as a powerregulation IAB node which is permitted to perform power management ofpower transmissions of a child node of the power regulation IAB node;transmitter circuitry configured to transmit a power regulation IAB nodedesignation to the power regulation IAB node.

In one example, a method in a donor Integrated Access and Backhaul (IAB)node in an Integrated Access and Backhaul (IAB) network, the methodcomprising: designating one or more IAB nodes of the Integrated Accessand Backhaul (IAB) network as a power regulation IAB node which ispermitted to perform power management of power transmissions of a childnode of the power regulation IAB node; transmitting a power regulationIAB node designation to the power regulation IAB node.

In one example, an Integrated Access and Backhaul (JAB) node of anIntegrated Access and Backhaul (IAB) network, the IAB node comprising:processor circuitry configured to generate, for each of plural child IABnodes, a maximum transmission power for distributed unit circuitrycomprising the plural child IAB nodes, the maximum transmission powerbeing configured in consideration of cross-link interference between theplural child IAB nodes; transmitter circuitry configured to transmit anindication of the maximum transmission power to the plural child IABnodes.

In one example, a method in an Integrated Access and Backhaul (IAB) nodeof an Integrated Access and Backhaul (IAB) network, the methodcomprising: generating, for each of plural child IAB nodes, a maximumtransmission power for distributed unit circuitry comprising the pluralchild IAB nodes, the maximum transmission power being configured inconsideration of cross-link interference between the plural child IABnodes; transmitting an indication of the maximum transmission power tothe plural child IAB nodes.

BRIEF DESCRIPTION OF DRAWINGS

The foregoing and other objects, features, and advantages of thetechnology disclosed herein will be apparent from the following moreparticular description of preferred embodiments as illustrated in theaccompanying drawings in which reference characters refer to the sameparts throughout the various views. The drawings are not necessarily toscale, emphasis instead being placed upon illustrating the principles ofthe technology disclosed herein.

FIG. 1 is a diagrammatic view of overall architecture for a 5G New Radiosystem.

FIG. 2 is a diagrammatic view illustrating a mobile networkinfrastructure using 5G signals and 5G base stations, and particularlyshowing a donor IAB node comprising an IAB network power managementcontroller and plural IAB nodes each comprising an IAB resourceconfiguration manager.

FIG. 3 is a diagrammatic view depicting an example of functional blockdiagrams for donor IAB node and a representative IAB node of FIG. 2.

FIG. 4 is a schematic view of an example generic communication systemcomprising an Integrated Access and Backhaul (IAB) network which mayserve as context for example embodiments and modes described herein.

FIG. 5 is a schematic view of portions of an example communicationsystem comprising an Integrated Access and Backhaul (IAB) networkwherein transmission power utilization is determined for an IAB node.

FIG. 6 is a schematic view of portions of an example communicationsystem comprising an Integrated Access and Backhaul (JAB) networkwherein an JAB node performs transmission power reporting, e.g.,transmission power utilization reporting and/or transmission powertransmission power headroom (PHR) reporting.

FIG. 7 is a schematic view of portions of an example communicationsystem comprising an Integrated Access and Backhaul (IAB) networkwherein an IAB node implements IAB node transmission powerprioritization rule(s) in certain circumstances.

FIG. 8 is a flowchart showing example, non-limiting, basic acts or stepsthat may be performed by an IAB node of FIG. 7 in conjunction with IABnode transmission power prioritization rule(s).

FIG. 9 is a schematic view of portions of an example communicationsystem comprising an Integrated Access and Backhaul (IAB) networkwherein an IAB node implements IAB DU transmission power governance incertain circumstances.

FIG. 10 is a flowchart showing example, non-limiting, basic acts orsteps that may be performed by an IAB node of FIG. 9 in conjunction withIAB node DU transmission power governance.

FIG. 11 is a schematic view of portions of an example communicationsystem comprising an Integrated Access and Backhaul (IAB) networkwherein transmission power utilization is determined for an IAB nodecomprising plural Mobile-Terminations (MTs).

FIG. 12 is a schematic view of portions of an example communicationsystem comprising an Integrated Access and Backhaul (IAB) networkwherein a donor IAB node selects one or more principal parent or familypower management IAB nodes.

FIG. 13 is a diagrammatic view showing example elements comprisingelectronic machinery which may comprise a wireless terminal, a radioaccess node, and a core network node according to an example embodimentand mode.

DESCRIPTION OF EMBODIMENTS

In one of its example aspects the technology disclosed herein concernsan Integrated Access and Backhaul (IAB) node that communicates over aradio interface. The IAB node comprises mobile-termination circuitry,distributed unit circuitry, and processor circuitry. Themobile-termination circuitry is configured to transmit over the radiointerface with a parent node. The distributed unit circuitry isconfigured to transmit over the radio interface with a child node. Theprocessor circuitry is configured to manage transmission power utilizedby the IAB node by taking into consideration both transmission by themobile-termination circuitry and transmission by the distributed unitcircuitry. Other example aspects of the technology disclosed hereinconcern transmission power reporting by such IAB node, transmissionpower prioritization by such JAB node; transmission power governance forthe distributed unit circuitry for such IAB node; and method ofoperating such IAB node(s).

In another of its example aspects the technology disclosed hereinconcerns a donor IAB node which is configured to select an IAB node toserve as a principal parent or family power management IAB node, andmethods of operation of such nodes.

In the following description, for purposes of explanation and notlimitation, specific details are set forth such as particulararchitectures, interfaces, techniques, etc. in order to provide athorough understanding of the technology disclosed herein. However, itwill be apparent to those skilled in the art that the technologydisclosed herein may be practiced in other embodiments that depart fromthese specific details. That is, those skilled in the art will be ableto devise various arrangements which, although not explicitly describedor shown herein, embody the principles of the technology disclosedherein and are included within its spirit and scope. In some instances,detailed descriptions of well-known devices, circuits, and methods areomitted so as not to obscure the description of the technology disclosedherein with unnecessary detail. All statements herein recitingprinciples, aspects, and embodiments of the technology disclosed herein,as well as specific examples thereof, are intended to encompass bothstructural and functional equivalents thereof. Additionally, it isintended that such equivalents include both currently known equivalentsas well as equivalents developed in the future, i.e., any elementsdeveloped that perform the same function, regardless of structure.

Thus, for example, it will be appreciated by those skilled in the artthat block diagrams herein can represent conceptual views ofillustrative circuitry or other functional units embodying theprinciples of the technology. Similarly, it will be appreciated that anyflow charts, state transition diagrams, pseudo code, and the likerepresent various processes which may be substantially represented incomputer readable medium and so executed by a computer or processor,whether or not such computer or processor is explicitly shown.

As used herein, the term “core network” can refer to a device, group ofdevices, or sub-system in a telecommunication network that providesservices to users of the telecommunications network. Examples ofservices provided by a core network include aggregation, authentication,call switching, service invocation, gateways to other networks, etc.

As used herein, the term “wireless terminal” can refer to any electronicdevice used to communicate voice and/or data via a telecommunicationssystem, such as (but not limited to) a cellular network. Otherterminology used to refer to wireless terminals and non-limitingexamples of such devices can include user equipment terminal, UE, mobilestation, mobile device, access terminal, subscriber station, mobileterminal, remote station, user terminal, terminal, subscriber unit,cellular phones, smart phones, personal digital assistants (“PDAs”),laptop computers, tablets, netbooks, e-readers, wireless modems, etc.

As used herein, the term “access node”, “node”, or “base station” canrefer to any device or group of devices that facilitates wirelesscommunication or otherwise provides an interface between a wirelessterminal and a telecommunications system. A non-limiting example of abase station can include, in the 3GPP specification, a Node B or “NB”,an enhanced Node B or eNodeB or eNB, a home eNB (“HeNB”), a gnodeB orgNB for a New Radio [“NR” ] technology system, and Integrated Access andBackhaul (IAB) node, or some other similar terminology.

As used herein, the term “telecommunication system” or “communicationssystem” can refer to any network of devices used to transmitinformation. A non-limiting example of a telecommunication system is acellular network or other wireless communication system. Furthermore,the “node” may comprise a portion of a gNB's architecture, inparticular, a gNB-DU (gNB Distributed Unit), which would be a logicalnode hosting RLC, MAC and PHY layers of the gNB, under the control of agNB-CU (gNB Central Unit), which would reside in a “donor node,” andhosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCPprotocols of the en-gNB that controls the operation of one or moregNB-DUs.

As used herein, the term “cellular network” or “cellular radio accessnetwork” can refer to a network distributed over cells, each cell servedby at least one fixed-location transceiver, such as a base station. Itshould also be noted that as used herein, a “cell” may be anycommunication channel that is specified by standardization or regulatorybodies to be used for International Mobile Telecommunications-Advanced(IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP aslicensed bands (e.g., frequency bands) to be used for communicationbetween an eNB and a UE. It should also be noted that in E-UTRA andE-UTRAN overall description, as used herein, a “cell” may be defined as“combination of downlink and optionally uplink resources.” The linkingbetween the carrier frequency of the downlink resources and the carrierfrequency of the uplink resources.

A cellular network using licensed frequency bands can include configuredcells. Configured cells can include cells of which a UE terminal isaware and in which it is allowed by a base station to transmit orreceive information. Examples of cellular radio access networks includeE-UTRAN, and any successors thereof (e.g., NUTRAN).

Configured cells” are those cells of which the UE is aware and isallowed by an eNB to transmit or receive information. “Configuredcell(s)” may be serving cell(s). The UE may receive system informationand perform the required measurements on all configured cells.“Configured cell(s)” for a radio connection may include a primary celland/or no, one, or more secondary cell(s). “Activated cells” are thoseconfigured cells on which the UE is transmitting and receiving. That is,activated cells are those cells for which the UE monitors the physicaldownlink control channel (PDCCH) and in the case of a downlinktransmission, those cells for which the UE decodes a physical downlinkshared channel (PDSCH). “Deactivated cells” are those configured cellsthat the UE is not monitoring the transmission PDCCH. It should be notedthat a “cell” may be described in terms of differing dimensions. Forexample, a “cell” may have temporal, spatial (e.g., geographical) andfrequency characteristics.

Any reference to a “resource” herein means “radio resource” unlessotherwise clear from the context that another meaning is intended. Ingeneral, as used herein a radio resource (“resource”) is atime-frequency unit that can carry information across a radio interface,e.g., either signal information or data information. An example of aradio resource occurs in the context of a “frame” of information that istypically formatted and prepared, e.g., by a node. In Long TermEvolution (LTE) a frame, which may have both downlink portion(s) anduplink portion(s), is communicated between the base station and thewireless terminal. Each LTE frame may comprise plural subframes. Forexample, in the time domain, a 10 ms frame consists of ten onemillisecond subframes. An LTE subframe is divided into two slots (sothat there are thus 20 slots in a frame). The transmitted signal in eachslot is described by a resource grid comprised of resource elements(RE). Each column of the two dimensional grid represents a symbol (e.g.,an OFDM symbol on downlink (DL) from node to wireless terminal; anSC-FDMA symbol in an uplink (UL) frame from wireless terminal to node).Each row of the grid represents a subcarrier. A resource element (RE) isthe smallest time-frequency unit for downlink transmission in thesubframe. That is, one symbol on one sub-carrier in the sub-framecomprises a resource element (RE) which is uniquely defined by an indexpair (k,l) in a slot (where k and l are the indices in the frequency andtime domain, respectively). In other words, one symbol on onesub-carrier is a resource element (RE). Each symbol comprises a numberof sub-carriers in the frequency domain, depending on the channelbandwidth and configuration. The smallest time-frequency resourcesupported by the standard today is a set of plural subcarriers andplural symbols (e.g., plural resource elements (RE)) and is called aresource block (RB). A resource block may comprise, for example, 84resource elements, i.e., 12 subcarriers and 7 symbols, in case of normalcyclic prefix.

Any reference to a “resource” herein means “radio resource” unlessotherwise clear from the context that another meaning is intended. Ingeneral, as used herein a radio resource (“resource”) is atime-frequency unit that can carry information across a radio interface,e.g., either signal information or data information.

An example of a radio resource occurs in the context of a “frame” ofinformation that is typically formatted and prepared, e.g., by a node.In Long Term Evolution (LTE) a frame, which may have both downlinkportion(s) and uplink portion(s), is communicated between the basestation and the wireless terminal. Each LTE frame may comprise pluralsubframes. For example, in the time domain, a 10 ms frame consists often one millisecond subframes. An LTE subframe is divided into two slots(so that there are thus 20 slots in a frame). The transmitted signal ineach slot is described by a resource grid comprised of resource elements(RE). Each column of the two dimensional grid represents a symbol (e.g.,an OFDM symbol on downlink (DL) from node to wireless terminal; anSC-FDMA symbol in an uplink (UL) frame from wireless terminal to node).Each row of the grid represents a subcarrier. A resource element (RE) isthe smallest time-frequency unit for downlink transmission in thesubframe. That is, one symbol on one sub-carrier in the sub-framecomprises a resource element (RE) which is uniquely defined by an indexpair (k,l) in a slot (where k and l are the indices in the frequency andtime domain, respectively). In other words, one symbol on onesub-carrier is a resource element (RE). Each symbol comprises a numberof sub-carriers in the frequency domain, depending on the channelbandwidth and configuration. The smallest time-frequency resourcesupported by the standard today is a set of plural subcarriers andplural symbols (e.g., plural resource elements (RE)) and is called aresource block (RB). A resource block may comprise, for example, 84resource elements, i.e., 12 subcarriers and 7 symbols, in case of normalcyclic prefix

In 5G New Radio (“NR”), a frame consists of 10 ms duration. A frameconsists of 10 subframes with each having 1 ms duration similar to LTE.Each subframe consists of 21 slots. Each slot can have either 14 (normalCP) or 12 (extended CP) OFDM symbols. A Slot is typical unit fortransmission used by scheduling mechanism. NR allows transmission tostart at any OFDM symbol and to last only as many symbols as requiredfor communication. This is known as “mini-slot” transmission. Thisfacilitates very low latency for critical data communication as well asminimizes interference to other RF links. Mini-slot helps to achievelower latency in 5G NR architecture. Unlike slot, mini-slots are nottied to the frame structure. It helps in puncturing the existing framewithout waiting to be scheduled. See, for example,https://www.rfwireless-world.com/5G/5G-NR-Mini-Slot.html, which isincorporated herein by reference. A mobile network used in wirelessnetworks may be where the source and destination are interconnected byway of a plurality of nodes. In such a network, the source anddestination may not be able to communicate with each other directly dueto the distance between the source and destination being greater thanthe transmission range of the nodes. That is, a need exists forintermediate node(s) to relay communications and provide transmission ofinformation. Accordingly, intermediate node(s) may be used to relayinformation signals in a relay network, having a network topology wherethe source and destination are interconnected by means of suchintermediate nodes. In a hierarchical telecommunications network, thebackhaul portion of the network may comprise the intermediate linksbetween the core network and the small subnetworks of the entirehierarchical network. Integrated Access and Backhaul (IAB) Nextgeneration NodeB use 5G New Radio communications such as transmittingand receiving NR User Plane (U-Plane) data traffic and NR Control Plane(C-Plane) data. Both, the UE and gNB may include addressable memory inelectronic communication with a processor. In one embodiment,instructions may be stored in the memory and are executable to processreceived packets and/or transmit packets according to differentprotocols, for example, Medium Access Control (MAC) Protocol and/orRadio Link Control (RLC) Protocol.

A mobile network used in wireless networks may be where the source anddestination are interconnected by way of a plurality of nodes. In such anetwork, the source and destination may not be able to communicate witheach other directly due to the distance between the source anddestination being greater than the transmission range of the nodes. Thatis, a need exists for intermediate node(s) to relay communications andprovide transmission of information. Accordingly, intermediate node(s)may be used to relay information signals in a relay network, having anetwork topology where the source and destination are interconnected bymeans of such intermediate nodes. In a hierarchical telecommunicationsnetwork, the backhaul portion of the network may comprise theintermediate links between the core network and the small sub-networksof the entire hierarchical network. Integrated Access and Backhaul (IAB)Next generation NodeB use 5G New Radio communications such astransmitting and receiving NR User Plane (U-Plane) data traffic and NRControl Plane (C-Plane) data. Both, the UE and gNB may includeaddressable memory in electronic communication with a processor. In oneembodiment, instructions may be stored in the memory and are executableto process received packets and/or transmit packets according todifferent protocols, for example, Medium Access Control (MAC) Protocoland/or Radio Link Control (RLC) Protocol.

A. Generic Architecture Description

FIG. 2 shows an example telecommunications system 20 comprising corenetwork 21 and plural wireless access nodes including donor IAB node 22and other IAB nodes 24, e.g., IAB nodes 24A, 24B, and 24C, which are notdonor IAB nodes; and plural user equipments (UE) 30 that are served byone or more of the access nodes. FIG. 2 further shows that the donor IABnode 22 may be connected to core network 21, e.g., by a wireline 31 orother suitable connection; and that wireless access links may connectthe donor IAB node 22, the IAB nodes 24, and the user equipments (UEs)30. FIG. 2 particularly shows, for example, that donor TAB node 22 isconnected by downlink donor backhaul link 32 and uplink donor backhaullink 33 to one or more IAB nodes 24. FIG. 2 further shows that an IABnode 24 may be connected by downlink backhaul link 34 and uplinkbackhaul link 35 to one or more child nodes, e.g., to a user equipment(UE) 30 or to another IAB node 24. It should be understood that someparts of operations and behaviors that are performed by the donor IABnode may be able to be performed by a parent IAB node.

With reference to FIG. 2, the present embodiments include a mobilenetwork infrastructure using 5G signals and 5G base stations (or cellstations). Depicted is a system diagram of a radio access networkutilizing IAB nodes, where the radio access network may comprise, forexample, one IAB-donor and multiple IAB-nodes. Different embodiments maycomprise different number of IAB-donor and IAB-node ratios. Herein, someof the IAB nodes may be referred to as IAB relay nodes. The IAB-node maybe a Radio Access Network (RAN) node that supports wireless access toUEs and wirelessly backhauls the access traffic. The IAB-donor may be aRAN node which may provide an interface to the core network to UEs andwireless backhauling functionality to IAB nodes. An IAB-node/donor mayserve one or more IAB nodes using wireless backhaul links as well as UEsusing wireless access links simultaneously. Accordingly, networkbackhaul traffic conditions may be implemented based on the wirelesscommunication system to a plurality of IAB nodes and UEs.

With further reference to FIG. 2, plural UEs 30 are depicted as incommunication with IAB nodes, for example, IAB nodes 24 and IAB donornode 22, via wireless access link(s). Additionally, the IAB-nodes (childnodes) may be in communication with other IAB-nodes and/or an IAB-donor(all of which may be considered IAB parent nodes) via wireless backhaullink. For example, a UE may be connected to an IAB-node which itself maybe connected to a parent IAB-node in communication with an IAB-donor,thereby extending the backhaul resources to allow for the transmissionof backhaul traffic within the network and between parent and child forintegrated access. The embodiments of the system provide forcapabilities needed to use the broadcast channel for carryinginformation bit(s) (on the physical channels) and provide access to thecore network.

The technology disclosed herein provides power management for IntegratedAccess and Backhaul (IAB) networks. Power management for IntegratedAccess and Backhaul (IAB) networks is considerably more complicated thanconventional power management for wireless terminals. Power managementfor Integrated Access and Backhaul (IAB) networks is complicated by thefact that, as shown in FIG. 3, an IAB node includes not only a mobiletermination entity such as Mobile-Termination (MT) 50, which mayfunction as a user equipment, but also a Distributed Unit (DU) 52. Asused herein, the Mobile-Termination (MT) 50 may also be referred to asmobile-termination circuitry, and Distributed Unit (DU) 52 may also bereferred to as distributed unit circuitry. The Mobile-Termination (MT)50 and Distributed Unit (DU) 52 may transmit simultaneously, and suchsimultaneous transmission has power management implications. Moreover,in some example embodiments and modes, the IAB node 24 may compriseplural Mobile-Terminations (MT) 50, which adds a further dimension tothe power management operation.

FIG. 2 further shows that, as one example aspect of the technologydisclosed herein, donor IAB node 22 may comprise IAB network powermanagement controller 36. One example purpose of IAB network powermanagement controller 36 may be to select one or more IAB nodes to serveas a “principal parent” or family power management IAB nodes. Forexample, the IAB network power management controller 36 of donor IABnode 22 may select IAB node 24B to be a family power management IABnode, as evidenced by the fact that IAB node 24B comprises family powermanagement controller 37. A node which is designated as a family powermanagement IAB node is responsible for regulating the power transmittedby its child IAB nodes. For example, the IAB node 24B of FIG. 2,designated as a family power management IAB node, regulates the powertransmission of not only wireless terminals served by IAB node 24B, butalso the power transmission of IAB node 24C and wireless terminalsserved by IAB node 24C. The donor IAB node 22 may also designated itselfas a family power management IAB node for regulating power transmissionof IAB node 24A and wireless terminals served by IAB node 24A, as wellas for regulating power transmission of IAB node 24B and wirelessterminals served by IAB node 24B.

FIG. 2 further shows that, as another example aspect of the technologydisclosed herein, one or more IAB nodes 24 may comprise IAB node powermanagement controller 38. In some example embodiments and modes, the IABnetwork power management controller 36 of donor IAB node 22 may worktogether with the IAB node power management controller(s) 38, but inother example embodiments and modes, the IAB node power managementcontroller(s) 38 may be provided independently from and thus form adistinctly separate innovation apart from IAB network power managementcontroller 36.

Example embodiments and modes featuring one or both of IAB network powermanagement controller 36 and IAB node power management controller 38facilitate enhanced and more efficient power management of theIntegrated Access and Backhaul (IAB) telecommunications system 20. Assuch, the technology disclosed herein provides power control and powermanagement considerably beyond the conventional power management forwireless terminals, and takes into consideration aspects and problems ofIntegrated Access and Backhaul (IAB) nodes.

FIG. 3 depicts an example of functional block diagrams for the donor JABnode 22 and the IAB node 24 (see FIG. 2). The donor IAB node 22 maycomprise at least one Central Unit (CU) 40 and at least one DistributedUnit (DU) 42. The Central Unit (CU) 40 is a logical entity managing theDU collocated in the donor IAB node 22 as well as the remote DUsresident in the IAB-nodes. The Central Unit (CU) 40 may also be aninterface to the core network 21, behaving as a RAN base station (e.g.,eNB or gNB).

In some embodiments, the Distributed Unit (DU) 42 is a logical entityhosting a radio interface (backhaul/access) for other child IAB-nodesand/or UEs. In one configuration, under the control of Central Unit (CU)40, the Distributed Unit (DU) 42 may offer a physical layer and Layer-2(L2) protocols, e.g., Medium Access Control (MAC), Radio Link Control(RLC), etc., while the Central Unit (CU) 40 may manage upper layerprotocols, such as Packet Data Convergence Protocol (PDCP), RadioResource Control (RRC), etc. As shown in FIG. 3, the Central Unit (CU)40 may host or comprise the IAB network power management controller 36,as hereinafter discussed.

As also shown in FIG. 3, an IAB node 24 may comprise Mobile-Termination(MT) 50 and Distributed Unit (DU) 52. In some example embodiments theDistributed Unit (DU) 52 may have the same functionality as theDistributed Unit (DU) 42 in the IAB-donor, whereas theMobile-Termination (MT) 50 may be a UE-like function that terminates theradio interface layers. As an example, the Mobile-Termination (MT) 50may function to perform at least one of: radio transmission andreception, encoding and decoding, error detection and correction,signaling, and access to a SIM. Either or both of the Mobile-Termination(MT) 50 and Distributed Unit (DU) 52 may comprise or host the IABresource configuration manager 38.

The DU may have all or parts of functions of an access node or gNB inFIG. 1 and an MT may have all or parts of functions of a UE. In otherwords, an access node or gNodeB may be rephrased by a CU and a DU, andthe UE may be rephrased as a MT.

Embodiments include a mobile network infrastructure where a number ofUEs are connected to a set of IAB-nodes and the IAB-nodes are incommunication with each other for relay and/or an IAB-donor using thedifferent aspects of the present embodiments. In some embodiments, theUE may communicate with the CU of the IAB-donor on the C-Plane using RRCprotocol and in other embodiments, using Service Data AdaptationProtocol (SDAP) and/or Packet Data Convergence Protocol (PDCP) radioprotocol architecture for data transport (U-Plane) through NR gNB. Insome embodiments, the DU of the IAB-node may communicate with the CU ofthe IAB-donor using 5G radio network layer signaling protocol: F1Application Protocol (F1-AP*) which is a wireless backhaul protocol thatprovides signaling services between the DU of an IAB-node and the CU ofan IAB-donor. That is, the protocol stack configuration may beinterchangeable, and different mechanism may be used.

In some aspects and or example embodiments and modes, a MobileTermination (MT) functionality—typically provided by the User Equipment(UE) terminals—may be implemented by Base Transceiver Stations (BTSs orBSs) nodes, for example, IAB nodes. In one embodiment, the MT functionsmay comprise common functions such as: radio transmission and reception,encoding and decoding, error detection and correction, signaling, andaccess to a SIM.

In a mobile network, an IAB child node may use the same initial accessprocedure (discovery) as an access UE to establish a connection with anIAB node/donor or parent-thereby attaching to the network or camping ona cell. In one embodiment, Radio Resource Control (RRC) protocol may beused for signaling between 5G radio network and UE, where RRC may haveat least two states (e.g., RRC_IDLE and RRC_CONNECTED) and statetransitions. The RRC sublayer may enable establishing of connectionsbased on the broadcasted system information and may also include asecurity procedure. The U-Plane may comprise of PHY, MAC, RLC and PDCPlayers.

FIG. 4 shows in more detail a generic example embodiment and mode ofarrangement and composition of certain functionalities and components ofdonor IAB node 22; an example, representative IAB node 24; and anexample, representative user equipment (UE) 30. It should be understoodthat each of the nodes of FIG. 4 comprise additional components andfunctionalities known to the person skilled in the art, and thatprimarily those pertinent to the technology disclosed herein areillustrated for sake of simplicity.

As understood from the foregoing, FIG. 4 shows that donor IAB node 22comprises central unit (CU) 40 and distributed unit (DU) 42. The centralunit (CU) 40 and distributed unit (DU) 42 may be realized by, e.g., becomprised of or include, one or more processor circuits, e.g., donornode processor(s) 46. The one or more node processor(s) 46 may be sharedby central unit (CU) 40 and distributed unit (DU) 42, or each of centralunit (CU) 40 and distributed unit (DU) 42 may comprise one or more nodeprocessor(s) 46. The IAB network power management controller 36 may becomprised or realized by donor node processor(s) 46. Central unit (CU)40 and distributed unit (DU) 42 may be co-located at a same node site,or alternatively one or more distributed units may be located at sitesremote from central unit (CU) 40 and connected thereto by a packetnetwork. The distributed unit (DU) 42 of donor IAB node 22 may comprisetransceiver circuitry 47, which in turn may comprise transmittercircuitry 48 and receiver circuitry 49. The transceiver circuitry 47includes antenna(e) for the wireless transmission. Transmitter circuitry48 includes, e.g., amplifier(s), modulation circuitry and otherconventional transmission equipment. Receiver circuitry 49 comprises,e.g., amplifiers, demodulation circuitry, and other conventionalreceiver equipment.

As shown in FIG. 4 the IAB-node 24, also known as wireless relay node24, in an example embodiment and mode comprises the IAB node mobiletermination (MT) unit 50 and IAB node distributed unit (DU) 52. The IABnode mobile termination (MT) unit 50 and IAB node distributed unit (DU)52 may be realized by, e.g., by comprised of or include, one or moreprocessor circuits, e.g., IAB node processor(s) 54. The one or more IABnode processor(s) 54 may be shared by IAB node mobile termination (MT)unit 50 and IAB node distributed unit (DU) 52, or each of IAB nodemobile termination (MT) unit 50 and IAB node distributed unit (DU) 52may comprise one or more IAB node processor(s) 54. The IAB node powermanagement controller 38 may comprise or be realized by IAB nodeprocessor(s) 54. The IAB node distributed unit (DU) 52 may comprise IABnode transceiver circuitry 57, which in turn may comprise IAB nodetransmitter circuitry 58 and IAB node receiver circuitry 59. The IABnode transceiver circuitry 57 includes antenna(e) for the wirelesstransmission. IAB node transmitter circuitry 58 may include, e.g.,amplifier(s), modulation circuitry and other conventional transmissionequipment. IAB node receiver circuitry 59 may comprise, e.g.,amplifiers, demodulation circuitry, and other conventional receiverequipment.

FIG. 4 shows child node 30, shown by way of example as user equipment(UE) 30, as comprising, in an example, non-limiting embodiment and mode,transceiver circuitry 60. The transceiver circuitry 60 in turn maycomprise transmitter circuitry 62 and receiver circuitry 64. Thetransceiver circuitry 60 includes antenna(e) for the wirelesstransmission. Transmitter circuitry 62 may include, e.g., amplifier(s),modulation circuitry and other conventional transmission equipment.Receiver circuitry 64 may comprise, e.g., amplifiers, demodulationcircuitry, and other conventional receiver equipment. FIG. 4 furthershows child node 30, which (as indicated before) may be a user equipmentor Integrated Access and Backhaul (IAB) node, as also comprising nodeprocessor circuitry, e.g., one or more node processor(s) 66, andinterfaces 68, including one or more user interfaces. Such userinterfaces may serve for both user input and output operations, and maycomprise (for example) a screen such as a touch screen that can bothdisplay information to the user and receive information entered by theuser. The user interface 68 may also include other types of devices,such as a speaker, a microphone, or a haptic feedback device, forexample.

In an example, non-limiting embodiment and mode shown in FIG. 4, thechild node 30 may include frame/message generator/handler 69. As isunderstood by those skilled in the art, in some telecommunicationssystem messages, signals, and/or data are communicated over a radio orair interface using one or more “resources”, e.g., “radio resource(s)”.The frame/message generator/handler 69 serves to handle messages,signals, and data received from other nodes.

Various aspects of JAB networks and nodes, and in some cases thevirtualization of such networks and nodes, are described in one or moreof the following United States Patent Applications, all of which areincorporated herein by reference:

-   -   U.S. Provisional Patent Application 62/780,068, filed Dec. 14,        2018, entitled “METHODS AND APPARATUS FOR CELL BARRING IN        WIRELESS RELAY NETWORKS”.    -   U.S. Provisional Patent Application 62/753,699, filed Oct. 31,        2018, entitled “METHODS AND APPARATUS FOR USING CONDITIONAL        HANDOVERS FOR WIRELESS”;    -   U.S. Provisional Patent Application 62/758,020, filed Nov. 8,        2018, entitled “NETWORK AND METHODS TO SUPPORT INTERDOMAIN        MOBILITY IN VIRTUALIZED RADIO ACCESS NETWORK”;    -   U.S. Provisional Patent Application 62/748,359, filed Oct. 19,        2018, entitled “METHODS AND APPARATUS FOR CAPABILITY SIGNALING        IN RADIO ACCESS NETWORK”;    -   U.S. Provisional Patent Application 62/748,015, filed Oct. 19,        2018, entitled “RADIO ACCESS NETWORK AND METHODS FOR EXPEDITED        NETWORK ACCESS”.    -   U.S. Provisional Patent Application 62/790,922, filed Jan. 10,        2019, entitled “RESOURCE MANAGEMENT FOR WIRELESS BACKHAUL        NETWORKS”.    -   U.S. Provisional Patent Application 62/790,922, filed Mar. 28,        2019, entitled “RESOURCE MANAGEMENT FOR WIRELESS BACKHAUL        NETWORKS”.    -   U.S. Provisional Patent Application 62/872,636, filed Jul. 10,        2019, entitled “FLEXIBLE UTILIZATION OF COMMUNICATION RESOURCES        TO SUPPORT BOTH ACCESS AND BACKHAUL”.

B: Determination of Transmission Power for IAB Nodes

As mentioned above, in one of its example aspects the technologydisclosed herein includes power management for an IAB node 24. In someexample embodiments and modes, such power management may involve orutilize an IAB node power management controller such as IAB node powermanagement controller 38 shown generally in FIG. 2.

As a generic example FIG. 5 shows a representative parent IAB node 70and a representative child IAB node 72. The parent IAB node 70 may be adonor IAB node such as donor IAB node 22 shown in FIG. 3 and FIG. 4, ora non-donor IAB node which also functions as a parent, such as IAB nodes24 of FIG. 2 and FIG. 4.

The parent IAB node 70 comprises parent node processor circuitry 74,which in turn may include or function as TAB resource configurationcontroller 76. The parent TAB node 70 further comprises parent nodetransceiver circuitry 77, which further may include transmittercircuitry 78 and receiver circuitry 79. In a first case that the parentIAB node 70 is a donor IAB node 22, the parent node processor circuitry74 may comprise or function as Central Unit (CU) 40, and the transceivercircuitry 47 may comprise or be realized by Distributed Unit (DU) 42,essentially in the manner shown in FIG. 4. In a second case that theparent IAB node 70 is not a donor IAB node 22 but another IAB node whichserves as a parent IAB node to a child IAB node, the parent nodeprocessor circuitry 74 may be shown by IAB node processor(s) 54 of IABnode 24 of FIG. 4, and the transceiver circuitry 47 may comprise or berealized by IAB node transceiver circuitry 57 essentially in the mannershown in FIG. 4. Regardless of whether the parent IAB node 70 is a donorIAB node 22 or an IAB node 24, the parent node processor circuitry 74may comprise the family power management controller 37.

The child IAB node 72 of FIG. 5 may be essentially an IAB node 24 asshown in FIG. 4. As such, even with reference to FIG. 5, the child IABnode 72 may also be referred to as the IAB node 24. The child IAB node72 like the IAB node 24 comprises Mobile-Termination (MT) 50 andDistributed Unit (DU) 52. One or more IAB node processor(s) 54 may serveto perform at least some functions of Mobile-Termination (MT) 50 and/orDistributed Unit (DU) 52. The IAB node processor(s) 54 may serve as theIAB node power management controller 38, as previously explained withreference to FIG. 4. Further, the Distributed Unit (DU) 52 may compriseIAB node transceiver circuitry 57, which in turn comprises IAB nodetransmitter circuitry 58 and IAB node receiver circuitry 59.

The child IAB node 72/IAB node 24 of FIG. 5 includes the IAB nodeprocessor(s) 54 and Mobile-Termination (MT) 50. In the exampleembodiment and mode of FIG. 5, the Mobile-Termination (MT) 50 includesreceiver circuitry that receives the power management configurationinformation from the parent node, e.g., the parent IAB node 70. Theradio resource configuration information may be received in a messagesuch as radio resource configuration information message 86.

In the example embodiment and mode of FIG. 5, IAB node power managementcontroller 38 comprises node transmission power manager 80. The nodetransmission power manager 80 serves to manage transmission powerutilized by the IAB node by taking into consideration both transmissionby the mobile-termination circuitry, e.g., Mobile-Termination (MT) 50,and transmission by the distributed unit circuitry, e.g., DistributedUnit (DU) 52. To do so, the node transmission power manager 80 comprisesPUSCH power controller 81; PUCCH power controller 82; PDSCH powercontroller 83; and PDCCH power controller 84. Each of these powercontrollers includes transmission power determination or transmissionpower calculation functionality for determining or calculating thetransmission power utilized on the respective channel by the respectiveunit, e.g., either Mobile-Termination (MT) 50 or Distributed Unit (DU)52. For example, PUSCH power controller 81 includes PUSCH transmissionpower calculator 86; PUCCH power controller 82 includes PUCCHtransmission power calculator 87; PDSCH power controller 83 includesPDSCH transmission power calculator 88; and, PDCCH power controller 84includes PDCCH transmission power calculator 89.

In an example embodiment and mode, and as explained below, each of PUSCHtransmission power calculator 86, PUCCH transmission power calculator87, PDSCH transmission power calculator 88, and PDCCH transmission powercalculator 89 may evaluate an expression or equation which is particularto the associated channel for making the respective calculation. In sodoing, in an example implementation, each of the power calculators mayutilize, for its associated respective channel, one or more of aconfigured maximum output power P_(CMAX) and configured grantinformation, e.g., ConfiguredGrantConfig. For this reason, FIG. 5 alsoshows each of PUSCH power controller 81, PUCCH power controller 82,PDSCH power controller 83, and PDCCH power controller 84 as comprising amemory or register to store such configured information. In particular,FIG. 5 shows PUSCH power controller 81 as comprising PUSCH configurationregister 91; PUCCH power controller 82 as comprising PUCCH configurationregister 92; PDSCH power controller 83 as comprising PDSCH configurationregister 93; and PDCCH power controller 84 as comprising PDCCHconfiguration register 94.

In an example, non-limiting embodiment and mode the PUSCH transmissionpower calculator 86 determines the PUSCH transmission powerP_(PUSCH,b,f,c)(i, j, q_(d), l) in PUSCH transmission occasion i usingEquation 1.

$\begin{matrix}{{P_{{PUSCH},b,f,c}\left( {i,j,q_{d},l} \right)} = {\min\begin{Bmatrix}\begin{matrix}\begin{matrix}{{P_{{CMAX},f,c}(i)},} \\{{P_{{O\_ PUSCH},b,f,c}(j)} + {10\log_{10}}}\end{matrix} \\{\left( {{2^{\mu} \cdot M_{{RB},b,f,c}^{PUSCH}}(i)} \right) +}\end{matrix} \\{{\alpha_{b,f,c}{(j) \cdot {PL}_{b,f,c}}\left( q_{d} \right)} +} \\{{\Delta_{{TF},b,f,c}(i)} + {f_{b,f,c,}\left( {i,l} \right)}}\end{Bmatrix}}} & {{Equation}1}\end{matrix}$

-   -   For sake of nomenclature, Equation 1 assumes that the        Mobile-Termination (MT) 50 transmits a PUSCH on active UL BWP b        of carrier f of serving cell c using parameter set configuration        with index j and PUSCH power control adjustment state with        index l. Equation 1 is understood with reference to it analogous        employment for PUSCH for a UE, as explained in TS38.213,        (V15.5.0) section 7.1, which is incorporated herein by reference        in its entirety, as well as Table 1 which provides further        explanation of terminology used in or pertinent to Equation 1.        At this juncture it is noted that the PUSCH transmission power        P_(PUSCH,b,f,c)(i, j, q_(d), l) may depend on P_(CMAX,f,c)(i),        which for the example embodiment and mode herein described is        the Mobile-Termination (MT) 50 configured maximum output power        for carrier f of serving cell c in PUSCH transmission        occasion i. Thus the expression utilized by PUSCH transmission        power calculator 86 for determining PUSCH transmission power by        the Mobile-Termination (MT) 50 may be essentially the same as        for determination of transmission power on PUSCH for a New Radio        wireless terminal or UE.

In an example, non-limiting embodiment and mode the PDSCH transmissionpower calculator 88 may determine the PDSCH transmission power inanalogous manner as PUSCH transmission power calculator 86 determinesthe PUSCH transmission power. That is, similar to Expression 1 utilizedby PUSCH transmission power calculator 86, PDSCH transmission powercalculator 88 may utilize a similar expression for transmitted PDSCHpower from the DU 52 to its children. This equation utilized by PDSCHtransmission power calculator 88 may be similar to the PUCCH Equation 1,however at least some parameters may be differently configurable. Forexample, PDSCH transmissions configured by ConfiguredGrantConfig, etc.,and parameters associated with Configured Grants for power control mayhave similar parameters similar to those of PUSCH, but which differ byreason of being for DU PDSCH instead of MT PUSCH. Other parameters mayhave to be adjusted, where necessary, because of assumed differences inDU and MT link budgets and transmitted powers. The determination forwhich parameters may be used may be based on RRC configuration, forexample for Configured Grant, but can also be made on the basis ofwhether or not there are specific quality of service, QoS, orreliability requirements associated with the PDSCH resources to be used.In general these parameters will be set by higher layers at thediscretion of the network administration & operation.

In an example, non-limiting embodiment and mode the PUCCH transmissionpower calculator 87 determines the PUCCH transmission powerP_(PUSCH,b,f,c)(i, q

, q_(d), l) in PUCCH transmission occasion i using Equation 2.

$\begin{matrix}{{P_{{PUCCH},b,f,c}\left( {i,q_{u},q_{d},l} \right)} = {\min\begin{Bmatrix}{{P_{{CMAX},f,c}(i)},} \\{{P_{{O\_ PUCCH},b,f,c}\left( q_{u} \right)} + {10\log_{10}}} \\{\left( {2^{\mu} \cdot {M_{{RB},b,f,c}^{PUCCH}(i)}} \right) +} \\{{{PL}_{b,f,c}\left( q_{d} \right)} + {\Delta_{F\_ PUCCH}(F)} +} \\{{\Delta_{{TF},b,f,c}(i)} + {g_{b,f,c}\left( {i,l} \right)}}\end{Bmatrix}}} & {{Equation}2}\end{matrix}$

For sake of nomenclature, Equation 2 assumes that the Mobile-Termination(MT) 50 transmits a PUCCH on active UL BWP b of carrier f in the primarycell c using PUCCH power control adjustment state with index l. Equation2 is understood with reference to it analogous employment for PUSCH fora UE, as explained in TS38.213, (V15.5.0) section 7.2.1, which isincorporated herein by reference in its entirety, as well as Table 2which provides further explanation of terminology used in or pertinentto Equation 2. At this juncture it is noted that the PUCCH transmissionpower P_(PUSCH,b,f,c)(i, q

, q_(d), l) may depend on P_(CMAX,f,c)(i) which for the exampleembodiment and mode herein described is the Mobile-Termination (MT) 50configured maximum output power for carrier f of serving cell c in PUCCHtransmission occasion i. Thus the expression utilized by PUCCHtransmission power calculator 87 for determining PUSCH transmissionpower by the Mobile-Termination (MT) 50 may be essentially the same asfor determination of transmission power on PUCCH for a New Radiowireless terminal or UE.

In an example, non-limiting embodiment and mode the PDCCH transmissionpower calculator 89 may determine the PDCCH transmission power inanalogous manner as PUCCH transmission power calculator 87 determinesthe PUCCH transmission power. That is, similar to Expression 2 utilizedby PUCCH transmission power calculator 87, PDCCH transmission powercalculator 89 may utilize a similar expression for transmitted PDCCHpower from the DU 52 to its children. This equation utilized by PDCCHtransmission power calculator 89 may be similar to the PDCCH Equation 2,however at least some parameters may be differently configurable. Forexample, PDCCH transmissions configured by ConfiguredGrantConfig, etc.,and parameters associated with Configured Grants for power control mayhave similar parameters similar to those of PUCCH, but which differ byreason of being for DU PDCCH instead of MT PUCCH. Other parameters mayhave to be adjusted, where necessary, because of assumed differences inDU and MT link budgets and transmitted powers. In an analogous manner asthe PDSCH; configuration may be performed by higher layers. Moreover,PDCCH resources that must be transmitted with higher reliability, asPDCCH transmissions configured via Configured Grant would be as well asother high reliability transmissions.

Thus in the example embodiment and mode of FIG. 5 an IAB node 24 isprovided with processor circuitry, e.g., IAB node processor(s) 54, whichis configured to determine transmission power utilization of the IABnode by determining each of:

-   -   (1) power utilization by the mobile-termination circuitry for        transmission on a Physical Uplink Shared Channel (PUSCH), as        determined by PUSCH power controller 81;    -   (2) power utilization by the mobile-termination circuitry for        transmission on a Physical Uplink Control Channel (PUCCH), as        determined by PUCCH power controller 82;    -   (3) power utilization by the distributed unit circuitry for        transmission on a Physical Downlink Shared Channel (PDSCH); as        determined by PDSCH power controller 83; and    -   (4) power utilization by the distributed unit circuitry for        transmission on a Physical Downlink Control Channel (PDCCH), as        determined by PDCCH power controller 84.    -   The total transmission power utilization may be a sum of each of        these four transmission power components.

C: Reporting of Transmission Power for IAB Nodes

FIG. 6 illustrates another example embodiment of an IAB network showingchild IAB node 72(6) with a transmission power reporting capability.Nodes, components, and functionalities of the example embodiment andmode of FIG. 6 which have same or similar reference numerals with thoseof FIG. 4 and/or FIG. 5 are understood to be the same or similar instructure and operation unless otherwise described herein or clear fromcontext.

The IAB node processor(s) 54 of child IAB node 72(6) of FIG. 6, andparticularly IAB node power management controller 38(6), is shown ascomprising IAB node transmission power report generator 120. The IABnode transmission power report generator 120 is configured to generate areport of transmission power of the IAB node for transmission to aparent node, e.g., to parent IAB node 70 shown in FIG. 6. The reportgenerated by IAB node transmission power report generator 120 mayinclude transmission power utilization and/or transmission powerheadroom (PHR). In an example implementation, mobile-terminationcircuitry Mobile-Termination (MT) 50 of child IAB node 72(6) maytransmit the report of transmission power to the parent node. Arrow 122in FIG. 6 shows transmission of the IAB node transmission power reportto parent IAB node 70.

In an example embodiment and mode, the IAB node transmission powerreport generator 120 generates the IAB node transmission power report tospecify each of the following:

-   -   (1) power utilization by the mobile-termination circuitry for        transmission on a Physical Uplink Shared Channel (PUSCH), as        determined by PUSCH power controller 81;    -   (2) power utilization by the mobile-termination circuitry for        transmission on a Physical Uplink Control Channel (PUCCH), as        determined by PUCCH power controller 82;    -   (3) power utilization by the distributed unit circuitry for        transmission on a Physical Downlink Shared Channel (PDSCH); as        determined by PDSCH power controller 83; and    -   (4) power utilization by the distributed unit circuitry for        transmission on a Physical Downlink Control Channel (PDCCH), as        determined by PDCCH power controller 84.

In another example embodiment and mode, the IAB node transmission powerreport generator 120 generates the IAB node transmission power report tospecify each of the following:

-   -   (a) power utilization by the mobile-termination circuitry for        transmission on both Physical Uplink Shared Channel (PUSCH), as        determined by PUSCH power controller 81, and power utilization        by the mobile-termination circuitry for transmission on a        Physical Uplink Control Channel (PUCCH), as determined by PUCCH        power controller 82;    -   (b) power utilization by the distributed unit circuitry for        transmission on both a Physical Downlink Shared Channel (PDSCH);        as determined by PDSCH power controller 83, and power        utilization by the distributed unit circuitry for transmission        on a Physical Downlink Control Channel (PDCCH), as determined by        PDCCH power controller 84

In view of its ability to generate the IAB node transmission powerreport generator 120 with specificity for (a)-(b), the IAB nodetransmission power report generator 120 is illustrated in FIG. 6 ascomprising both MT transmission power report generator 124 and DUtransmission power report generator 126.

In an example embodiment and mode, IAB node transmission power reportgenerator 120 may additionally or alternatively generate the IAB nodetransmission power report to include a report of transmission powerheadroom (PHR) in addition to or as an alternative to transmission powerutilization. As used herein, transmission power headroom (PHR) may be adifference between a maximum transmission power allocated to the childIAB node 72, or to its Mobile-Termination (MT) 50 or to its IAB nodeprocessor(s) 54, and actual transmission power utilization by the childIAB node 72, or by its Mobile-Termination (MT) 50, or by its IAB nodeprocessor(s) 54. Such maximum transmission power allocation may bestored in one or more of PUSCH configuration register 91, PUCCHconfiguration register 92, PDSCH configuration register 93, and/or PDCCHconfiguration register 94, or may be derived therefrom. As indicatedabove, the maximum permitted transmission power for themobile-termination circuitry and the maximum permitted transmissionpower for the distributed unit circuitry may be configurable, e.g., byparent IAB node 70. FIG. 6 thus shows IAB node transmission power reportgenerator 120 as optionally comprising transmission power headroomreport generator 127. The transmission power headroom report generator127 thus may include an indication of the transmission power headroom(PHR) in the IAB node transmission power report 122. The indication oftransmission power headroom (PHR) may be a collective value representingtransmission power headroom (PHR) for the entire child IAB node 72, andmay include more specify information such as transmission power headroom(PHR) or one or both of the Distributed Unit (DU) 52 and the IAB nodeprocessor(s) 54 of child IAB node 72. Alternately or additionally, thepower headroom of MT transmission power may be reported. For an MT of anIAB node, the power headroom 9 PHR) may be reported in a manner similarto New radio uplink transmission power control, TPC, at an UE terminal.The maximum transmission power information may of DU part be indicatedto a parent node.

The IAB node transmission power report generated by IAB nodetransmission power report generator 120 may be formatted in any suitablemanner. For example, the IAB node transmission power report may comprisean information element that includes a total transmission powerutilization for the child IAB node 72, with other information elementsor sub-information elements that specify each of (1)-(4) and/or (a)-(b)listed above. In an example implementation in which the transmissionpower headroom report generator 127 is present and active, the IAB nodetransmission power report 122 may include, either in the sameinformation element, e.g., as sub-information elements, or in anadditional information element, the transmission power headroom (PHR)reports for the entire child IAB node 72 and/or its Mobile-Termination(MT) 50 and Distributed Unit (DU) 52.

FIG. 6 shows that IAB node 70 may comprise an IAB network powermanagement controller 36. The receiver circuitry 79 of parent IAB node70 may receive the IAB node transmission power report, which in turn maybe utilized by child IAB node transmission power report processor 128.The IAB node transmission power report may be used by the parent node toschedule resources on the child MT or DU, especially on the child, itcan be used to dictate the modulation and coding schemes to be used andthe resources the child transmissions can occupy. The IAB nodetransmission power report may also or alternatively be used to allocateresources to the DU/MT, and/or to re-route traffic backhauled on a childlink.

D: Prioritization of Transmission Power for IAB Nodes

FIG. 7 illustrates another example embodiment of an IAB network showingchild IAB node 72(7) with a transmission power prioritizationcapability. Nodes, components, and functionalities of the exampleembodiment and mode of FIG. 7 which have same or similar referencenumerals with those of FIG. 4 and/or FIG. 5 and/or FIG. 6 are understoodto be the same or similar in structure and operation unless otherwisedescribed herein or clear from context.

The IAB node processor(s) 54 of child IAB node 72(7) of FIG. 7, andparticularly IAB node power management controller 38(7), is shown ascomprising IAB node transmission power prioritization rule register ormemory 130, herein also referred to simply as IAB node transmissionpower prioritization rule(s) 130.

In the example embodiment and mode of FIG. 7, the IAB node powermanagement controller 38(7) performs example, representative acts orsteps shown in FIG. 8. Act 8-1 comprises determining a totaltransmission power utilization of the IAB node taking into considerationboth the transmission by the mobile-termination circuitry and thetransmission by the distributed unit circuitry. Act 8-2 comprisescomparing the total transmission power utilization with a maximumpermitted total transmission power. Act 8-3 is performed when the totaltransmission power utilization of the IAB node is in a predeterminedneighborhood of the maximum permitted total transmission power. Act 8-3comprises using a prioritization rule to govern operation of at leastone of the mobile-termination circuitry and the distributed unitcircuitry. The prioritization rule utilized in act 8-3 may be stored asIAB node transmission power prioritization rule(s) 130, and may have theresult or consequences described below.

The IAB node transmission power prioritization rule(s) 130 may beimplemented as logic or coded instructions which are configured toobtain an intended transmission power strategy. The IAB nodetransmission power prioritization rule(s) 130 may be configured at theparent IAB node 70(7), e.g., either pre-configured or downloaded from aparent IAB node such as an IAB node that serves as a family powermanagement JAB node. As understood from the foregoing, the maximumtransmitted power permitted for child IAB node 72(7) may beconfigurable, e.g., for both the DU and the MT.

As mentioned above, act 8-3 is performed when the total transmissionpower utilization of the IAB node is in a predetermined neighborhood ofthe maximum permitted total transmission power. The predeterminedneighborhood may be plus or minus a predetermined percentage of themaximum permitted transmission power. The predetermined neighborhood mayitself be configured, e.g., preconfigured at the child IAB node 72(7) ordownloaded by the network.

On example of an IAB node transmission power prioritization rule is toprioritize the transmissions by the mobile-termination circuitryrelative to the transmissions by the distributed unit circuitry whendesirable or necessary, e.g., when the total transmission powerutilization of the IAB node is in a predetermined neighborhood of themaximum permitted total transmission power. For example, in the eventthat total transmitted power is near its maximum, operation of IAB nodetransmission power prioritization rule(s) 130 may privilege or favor theMobile-Termination (MT) 50. In other words, the MT power isprivileged—that is, the parent—child link is privileged over thechild-grandchildren link(s); i.e., lower downlink capacity onchild-grandchildren links to ensure reliability of the parent childlink. Implementation of such a MT-favoring rule may include or causedropping transmissions on child-grandchild links.

Another example of an IAB node transmission power prioritization rule isto prioritize the transmissions by the distributed unit circuitryrelative to the transmissions by the mobile-termination circuitry whendesirable or necessary, e.g., when the total transmission powerutilization of the IAB node is in a predetermined neighborhood of themaximum permitted total transmission power. For example, in the eventthat total transmitted power is near its maximum, operation of IAB nodetransmission power prioritization rule(s) 130 may privilege or favor theDistributed Unit (DU) 52, ensuring reliability of the child-grandchildlinks.

In the event that the IAB node transmission power prioritization rule(s)130 are invoked, the child IAB node 72(7) may send a report of suchinvocation and its consequences to a parent node such as parent IAB node70. FIG. 7 thus shows IAB node transmission power report generator 120as comprising an optional prioritization rule(s) invocation reportgenerator 132, which, as an optional feature for this FIG. 7 exampleembodiment and mode, may send a prioritization rule(s) invocation report134 to parent IAB node 70.

E: Governance of Du Transmission Power for IAB Nodes

FIG. 9 illustrates another example embodiment of an IAB network showingchild IAB node 72(9) with DU transmission power governance capability.Nodes, components, and functionalities of the example embodiment andmode of FIG. 9 which have same or similar reference numerals with thoseof FIG. 4, FIG. 5, FIG. 6, and/or FIG. 7 are understood to be the sameor similar in structure and operation unless otherwise described hereinor clear from context.

In the example embodiment and mode of FIG. 9, the DU transmission powerfor PDCCH and/or PDSCH at a DU in an IAB node may be configured by a CUor a parent IAB node. One purpose for such configuration may be tominimize the cross-link interference (CLI) level by setting/configuringthe DU transmission power per IAB node.

The IAB node processor(s) 54 of child IAB node 72(9) of FIG. 9, andparticularly IAB node power management controller 38(7), is shown ascomprising IAB node DU transmission power governor 140, herein alsoreferred to simply as DU power governor 140. FIG. 9 further shows familypower management controller 37 of parent IAB node 70(9) as comprising achild node transmission power controller 144 for one or plural child IABnodes for which parent IAB node 70(9) may have family control orsupervisory authority. For example, FIG. 9 shows family power managementcontroller 37 as comprising child node transmission power controller 144₁ through child node transmission power controller 144 _(k) for each ofk integer number of child IAB nodes which for which parent IAB node70(9) may have parental power control. Each child node transmissionpower controller 144 is shown as further comprising a MT maximum powercontroller 146 and a DU maximum power controller 148, as well as asignal generator 150. The MT maximum power controller 146 may controlmaximum transmission power for one or both of PUSCH and PUCCH for theMobile-Termination (MT) 50 of child IAB node 72(9); the DU maximum powercontroller 148 may control maximum transmission power for one or both ofPDSCH and PDCCH for the Distributed Unit (DU) 52 of child IAB node72(9).

FIG. 9 further shows that the signal generator 150 of child nodetransmission power controller 144 may generate a DU maximum transmissionpower control signal 152 which is transmitted by transmitter circuitry78 of parent IAB node 70(9) to child IAB node 72(9), and whichspecifies, for example, a maximum DU transmission power for theDistributed Unit (DU) 52 of child IAB node 72(9). The DU maximumtransmission power control signal 152 may be used by DU power governor140 for controlling the maximum power of Distributed Unit (DU) 52 sothat transmission power of Distributed Unit (DU) 52 of the particularchild IAB node 72(9) shown in FIG. 9 does not, or has less likelihoodof, causing cross-link interference with transmissions of other IABnodes. Thus, the DU maximum transmission power control signal 152, andthe DU power governor 140 which receives and operates on the DU maximumtransmission power control signal 152, takes into consideration actualor possible cross-link interference with transmissions of other JABnodes.

The DU transmission power for PDSCH may be configured separately fromthat for PDCCH. In other words the DU power governor 140 may govern thetransmission power separately for PDSCH and PDCCH.

FIG. 10 shows example, representative basic acts or steps that may beperformed by the child IAB node 72(9) of FIG. 9. Act 10-1 comprisesmaking a comparison of a determined transmission power utilization bythe distributed unit circuitry with a configured maximum transmissionpower for the distributed unit circuitry. Act 10-2 comprises, inaccordance with the comparison, governing actual transmission power ofthe distributed unit circuitry. Such act of governing actualtransmission power of the distributed unit circuitry may includereduction of DU transmission power, or even dropping links orconnections.

The parent IAB node 70(9) of FIG. 9 has thus been shown as comprisingparent node processor circuitry 74 which is configured to generate, foreach of plural child IAB nodes, a maximum transmission power fordistributed unit circuitry comprising the plural child IAB nodes. Asindicated, one example purpose of maximum transmission power being soconfigured is in consideration of cross-link interference between theplural child IAB nodes. The parent IAB node 709(9) also comprisestransmitter circuitry 78 configured to transmit an indication of themaximum transmission power to the plural child IAB nodes.

The DU maximum transmission power control signal 152 may be transmittedfrom parent IAB node 70(9) to child IAB node 72(9) in any suitablemanner. For example, DU maximum transmission power control signal 152may be transmitted via an F1-AP interface (see FIG. 1), as or in amedium access control (MAC) control element, or by downlink controlinformation (DCI).

In the event that the IAB node DU transmission power governance isinvoked, the child IAB node 72(9) may send a report of such invocationand its consequences to a parent node such as parent IAB node 70(9).FIG. 9 thus shows IAB node DU transmission power report generator 140 ascomprising DU governance invocation report generator 154, which, as anoptional feature for this FIG. 9 example embodiment and mode, may send aDU governance invocation report, or DU power report 156, to parent IABnode 70(9).

F: Transmission Power for IAB Nodes with Multiple MTS

Example embodiments and modes described herein have thus far illustratedthe child IAB node 72 as comprising one Mobile-Termination (MT) 50.However, for each of the example embodiments and modes described hereinthe child IAB node 72 may comprise plural Mobile-Terminations (MTs) 50,in a manner such as illustrated in FIG. 11. As shown in FIG. 11, childIAB node 72(11) may comprise plural Mobile-Terminations (MTs) 50, suchas Mobile-Termination (MT) 50 ₁ through Mobile-Termination (MT) 50 _(n).In addition, for each Mobile-Termination (MT) 50 the IAB node powermanagement controller 38 may comprise PUSCH power controller 81 andPUCCH power controller 82. In other words, the IAB node power managementcontroller 38 may comprise PUSCH power controller 81 ₁ and PUCCH powercontroller 82 ₁ for Mobile-Termination (MT) 501, and PUSCH powercontroller 81 _(n) and PUCCH power controller 82 _(n) forMobile-Termination (MT) 50 _(n).

In general these plural MTs may operate independently of each other withdifferent power control parameters independently, because of differentRF front ends because they would transceive on different bands.Likewise, they may operate dependently if these MTs share the samefrequency band. In either case, the MTs may be separately signaled andpower controlled and may separately report their power headrooms. Thus,at least some aspects of the technology disclosed herein may be appliedto the PUSCH of the MT if a single MT entity existed in the IAB node, orif multiple MTs on different carriers on different frequency bands wereimplemented in the IAB node.

G: Designation of IAB Nodes as Power Management Parents

FIG. 12 illustrates another example embodiment of an IAB network showingdonor IAB node 22(12) as comprising IAB network power managementcontroller 36. One example purpose of IAB network power managementcontroller 36 may be to enable the donor IAB node 22(12) to select oneor more IAB nodes to serve as a “principal parent” or family powermanagement IAB nodes. Examples of IAB nodes that may serve as familypower management IAB nodes are shown as IAB nodes 70 in one or more ofFIG. 6, FIG. 7, and FIG. 9. Nodes, components, and functionalities ofthe example embodiment and mode of FIG. 9 which have same or similarreference numerals with those of FIG. 4, FIG. 5, FIG. 6, FIG. 7, and/orFIG. 9 are understood to be the same or similar in structure andoperation unless otherwise described herein or clear from context.

FIG. 12 shows that node processor(s) 46 of donor IAB node 22(12) maycomprise logic 160 for selecting family power management nodes(s). Thefamily power management nodes(s) logic 160 preferably comprises IABnetwork power management controller 36, and may be a set of codedinstructions on non-transient media that may be executed by nodeprocessor(s) 46 of donor IAB node 22(12). FIG. 12 shows by arrow 162that family power management nodes(s) logic 160 has selected IAB node24B to be a family power management nodes. As a result of suchselection, 24B is shown as comprising family power management controller37. A node which is designated as a family power management IAB node isresponsible for regulating the power transmitted by its child IAB nodes.For example, the IAB node 24B of FIG. 12, designated as a family powermanagement IAB node, regulates the power transmission of not onlywireless terminals served by JAB node 24B, but also the powertransmission of IAB node 24C and wireless terminals served by IAB node24C. The donor IAB node 22(12) may also designated itself as a familypower management IAB node for regulating power transmission of IAB node24A and wireless terminals served by IAB node 24A, as well as forregulating power transmission of IAB node 24B and wireless terminalsserved by IAB node 24B.

Thus, the example embodiment and mode encompasses a donor IntegratedAccess and Backhaul (IAB) node in an Integrated Access and Backhaul(IAB) network which may comprise processor circuitry and transmittercircuitry. The processor circuitry is configured to designate one ormore IAB nodes of the Integrated Access and Backhaul (IAB) network as apower regulation IAB node which is permitted to perform power managementof power transmissions of a child node of the power regulation IAB node.The transmitter circuitry is configured to transmit a power regulationIAB node designation, represented by arrow 162, to the power regulationIAB node.

The criteria for selection of a candidate IAB node as a family powermanagement IAB node may be coded or programmed into family powermanagement nodes(s) logic 160. Such criteria may be based on or considersuch factors location/role of the IAB node 24 in relation to overall orlocal network topology, e.g., the number of other IAB nodes for whichthe candidate node is parent, and the history of traffic or utilizationof such candidate node and its children.

It should be understood that, unless otherwise indicate or apparent fromcontext, one or more of the features of the example embodiments andmodes herein, such as for example FIG. 4, FIG. 5, FIG. 6, FIG. 7, FIG.9, FIG. 11, and FIG. 12, may be utilized in conjunction with featuresfrom other one or more of such example embodiments and modes.

Certain units and functionalities of the systems 20 may be implementedby electronic machinery. For example, electronic machinery may refer tothe processor circuitry described herein, such as IAB node processor(s)54/74, donor node processor(s) 46, and node processor(s) 66. Moreover,the term “processor circuitry” is not limited to mean one processor, butmay include plural processors, with the plural processors operating atone or more sites. Moreover, as used herein the term “server” is notconfined to one server unit, but may encompasses plural servers and/orother electronic equipment, and may be co-located at one site ordistributed to different sites. With these understandings, FIG. 13 showsan example of electronic machinery, e.g., processor circuitry, ascomprising one or more processors 290, program instruction memory 292;other memory 294 (e.g., RAM, cache, etc.); input/output interfaces 296and 297, peripheral interfaces 298; support circuits 299; and busses 300for communication between the aforementioned units. The processor(s) 290may comprise the processor circuitries described herein, for example,JAB node processor(s) 54, donor node processor(s) 46, and nodeprocessor(s) 66.

An memory or register described herein may be depicted by memory 294, orany computer-readable medium, may be one or more of readily availablememory such as random access memory (RAM), read only memory (ROM),floppy disk, hard disk, flash memory or any other form of digitalstorage, local or remote, and is preferably of non-volatile nature, asand such may comprise memory. The support circuits 299 are coupled tothe processors 290 for supporting the processor in a conventionalmanner. These circuits include cache, power supplies, clock circuits,input/output circuitry and subsystems, and the like.

Although the processes and methods of the disclosed embodiments may bediscussed as being implemented as a software routine, some of the methodsteps that are disclosed therein may be performed in hardware as well asby a processor running software. As such, the embodiments may beimplemented in software as executed upon a computer system, in hardwareas an application specific integrated circuit or other type of hardwareimplementation, or a combination of software and hardware. The softwareroutines of the disclosed embodiments are capable of being executed onany computer operating system, and is capable of being performed usingany CPU architecture.

The functions of the various elements including functional blocks,including but not limited to those labeled or described as “computer”,“processor” or “controller”, may be provided through the use of hardwaresuch as circuit hardware and/or hardware capable of executing softwarein the form of coded instructions stored on computer readable medium.Thus, such functions and illustrated functional blocks are to beunderstood as being either hardware-implemented and/orcomputer-implemented, and thus machine-implemented.

In terms of hardware implementation, the functional blocks may includeor encompass, without limitation, digital signal processor (DSP)hardware, reduced instruction set processor, hardware (e.g., digital oranalog) circuitry including but not limited to application specificintegrated circuit(s) [ASIC], and/or field programmable gate array(s)(FPGA(s)), and (where appropriate) state machines capable of performingsuch functions.

In terms of computer implementation, a computer is generally understoodto comprise one or more processors or one or more controllers, and theterms computer and processor and controller may be employedinterchangeably herein. When provided by a computer or processor orcontroller, the functions may be provided by a single dedicated computeror processor or controller, by a single shared computer or processor orcontroller, or by a plurality of individual computers or processors orcontrollers, some of which may be shared or distributed. Moreover, useof the term “processor” or “controller” may also be construed to referto other hardware capable of performing such functions and/or executingsoftware, such as the example hardware recited above.

Nodes that communicate using the air interface also have suitable radiocommunications circuitry. Moreover, the technology disclosed herein mayadditionally be considered to be embodied entirely within any form ofcomputer-readable memory, such as solid-state memory, magnetic disk, oroptical disk containing an appropriate set of computer instructions thatwould cause a processor to carry out the techniques described herein.

Moreover, each functional block or various features of the wirelessaccess node 22, the wireless relay node 24, and/or the wirelessterminal/wireless node 30 used in each of the aforementioned embodimentsmay be implemented or executed by circuitry, which is typically anintegrated circuit or a plurality of integrated circuits. The circuitrydesigned to execute the functions described in the present specificationmay comprise a general-purpose processor, a digital signal processor(DSP), an application specific or general application integrated circuit(ASIC), a field programmable gate array (FPGA), or other programmablelogic devices, discrete gates or transistor logic, or a discretehardware component, or a combination thereof. The general-purposeprocessor may be a microprocessor, or alternatively, the processor maybe a conventional processor, a controller, a microcontroller or a statemachine. The general-purpose processor or each circuit described abovemay be configured by a digital circuit or may be configured by ananalogue circuit. Further, when a technology of making into anintegrated circuit superseding integrated circuits at the present timeappears due to advancement of a semiconductor technology, the integratedcircuit by this technology is also able to be used.

It will be appreciated that the technology disclosed herein is directedto solving radio communications-centric issues and is necessarily rootedin computer technology and overcomes problems specifically arising inradio communications. Moreover, the technology disclosed herein improvesbasic functioning of an Integrated Access and Backhaul (IAB) network,e.g., methods and procedures to deal with power management.

For example, in one or more of its various aspects the technologydisclosed herein concerns and/or provides:

-   -   The use of measurement reports, e.g., of power headroom taking        into account DU transmissions and transmissions of MTs both        individual and simultaneously. A power headroom reporting (PHR)        is provided for IAB nodes; which is especially useful given the        fact that MTs may also be transmitting simultaneously as the DU        is in a given IAB node.    -   Power control under the control of a “Principal Parent” (“PP”)        who is responsible for regulating the transmitted power over its        children. The PP is designated as such by the CU.    -   Rules for transmission cessation on one or more entities (MT(s)        and/or DU) that allow configurable prioritization of which        entities are privileged for transmissions.    -   Rules for Power Control for IAB child nodes.

Release 16 of 3GPP's cellular telephony specifications promise theintroduction of features to support interactive access and backhaul(IAB). The technology disclosed herein provides IAB nodes with powermanagement functionality which is useful for many reasons. For example,it is important for capacity management purposes in the overall IABnetwork to manage inter-cell interference (and each node may compriseone or more cells). As a second example reason, resource allocation inany IAB nodes' DUs may be constrained by its overall transmission power.For a third example reason, both DU and MT transmissions must meet somesort of emission requirements whether via spectral emission mask (SEM)or adjacent channel leakage ratio (ACLR); and this must be achieved withClass A amplifiers; hence transmission below maximum transmitted powershould be consistently achieved to meet these requirements.

Although the description above contains many specificities, these shouldnot be construed as limiting the scope of the technology disclosedherein but as merely providing illustrations of some of the presentlypreferred embodiments of the technology disclosed herein. Thus the scopeof the technology disclosed herein should be determined by the appendedclaims and their legal equivalents. Therefore, it will be appreciatedthat the scope of the technology disclosed herein fully encompassesother embodiments which may become obvious to those skilled in the art,and that the scope of the technology disclosed herein is accordingly tobe limited by nothing other than the appended claims, in which referenceto an element in the singular is not intended to mean “one and only one”unless explicitly so stated, but rather “one or more.” Theabove-described embodiments could be combined with one another. Allstructural, chemical, and functional equivalents to the elements of theabove-described preferred embodiment that are known to those of ordinaryskill in the art are expressly incorporated herein by reference and areintended to be encompassed by the present claims. Moreover, it is notnecessary for a device or method to address each and every problemsought to be solved by the technology disclosed herein, for it to beencompassed by the present claims. Furthermore, no element, component,or method step in the present disclosure is intended to be dedicated tothe public regardless of whether the element, component, or method stepis explicitly recited in the claims.

CROSS REFERENCE

This Nonprovisional application claims priority under 35 U.S.C. § 119 onprovisional Application No. 62/879,309 on Jul. 26, 2019, the entirecontents of which are hereby incorporated by reference.

1. An Integrated Access and Backhaul (IAB) node that communicates over aradio interface, the IAB node comprising: mobile-termination circuitryconfigured to transmit over the radio interface with a parent node;distributed unit circuitry configured to transmit over the radiointerface with a child node; processor circuitry configured to managetransmission power utilized by the IAB node by taking into considerationboth transmission by the mobile-termination circuitry and transmissionby the distributed unit circuitry.
 2. The IAB node of claim 1, whereinthe processor circuitry configured to determine transmission powerutilization of the IAB node by determining each of: (a) powerutilization by the mobile-termination circuitry for transmission on aPhysical Uplink Shared Channel (PUSCH); (b) power utilization by themobile-termination circuitry for transmission on a Physical UplinkControl Channel (PUCCH); (c) power utilization by the distributed unitcircuitry for transmission on a Physical Downlink Shared Channel(PDSCH); (d) power utilization by the distributed unit circuitry fortransmission on a Physical Downlink Control Channel (PDCCH).
 3. The IABnode of claim 2, wherein the processor circuitry is configured togenerate a report of transmission power utilization of the IAB node andwherein the mobile-termination circuitry is configured to transmit thereport of transmission power utilization to the parent node. 4.(canceled)
 5. (canceled)
 6. (canceled)
 7. A donor Integrated Access andBackhaul (IAB) node in an Integrated Access and Backhaul (IAB) network,the donor IAB node comprising: processor circuitry configured todesignate one or more IAB nodes of the Integrated Access and Backhaul(IAB) network as a power regulation IAB node which is permitted toperform power management of power transmissions of a child node of thepower regulation IAB node; transmitter circuitry configured to transmita power regulation IAB node designation to the power regulation IABnode.
 8. The donor IAB node of claim 7, wherein the power regulation IABnode designation authorizes the power regulation IAB node to manage bothtransmission power by a mobile-termination circuitry of the child nodeand transmission power by a distributed unit circuitry of the childnode.
 9. (canceled)
 10. (canceled)
 11. An Integrated Access and Backhaul(IAB) node of an Integrated Access and Backhaul (IAB) network, the IABnode comprising: processor circuitry configured to generate, for each ofplural child IAB nodes, a maximum transmission power for distributedunit circuitry comprising the plural child IAB nodes, the maximumtransmission power being configured in consideration of cross-linkinterference between the plural child IAB nodes; transmitter circuitryconfigured to transmit an indication of the maximum transmission powerto the plural child IAB nodes.
 12. The IAB node of claim 11, wherein forat least one of the plural child IAB nodes the maximum transmissionpower for the distributed unit circuitry is one or both of configuredmaximum transmission power for the Physical Downlink Shared Channel(PDSCH) and configured maximum transmission power for the PhysicalDownlink Control Channel (PDCCH).
 13. (canceled)
 14. (canceled)